-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prep for 1.34.2 release (go1.21 support) #69
prep for 1.34.2 release (go1.21 support) #69
Conversation
/lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
Do we really want to cut a release, knowing that generation is still broken AFAIK? |
Signed-off-by: Jordan Keister <jordan@nimblewidget.com>
57700a9
to
bde9676
Compare
/lgtm |
/cherry-pick release-v1.34 |
@grokspawn: new pull request created: #70 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cherry-pick release-v1.34 |
@grokspawn: new pull request could not be created: failed to create pull request against operator-framework/ansible-operator-plugins#release-v1.34 from head openshift-cherrypick-robot:cherry-pick-69-to-release-v1.34: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for openshift-cherrypick-robot:cherry-pick-69-to-release-v1.34."}],"documentation_url":"https://docs.github.com/rest/pulls/pulls#create-a-pull-request"} In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/cherry-pick release-v1.34 |
@grokspawn: new pull request created: #72 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Description of the change:
Motivation for the change: